EXCEPTION_ACCESS_VIOLATION when not saving on switching to Read-Only

Mathias Mamsch - Sat Mar 12 04:47:42 EST 2011
We had a script once with a bug, that would render DOORS unstable, which also created an attribute. It did not crash immediately, however one tried to start the attribute dialog DOORS crashed. I bet that there is an issue with the DXL scriptyou used. Can you post it? Regards, Mathias

Mathias Mamsch - Sat Mar 12 07:43:45 EST 2011
I found the code with the rather innocent looking code, that will make DOORS so unstable that it will crash (but not in the code, just afterwards).

See here

Regards, Mathias

Dangthrimble - Mon Mar 21 05:30:21 EDT 2011
Attached is the code, though it has developed somewhat since my original post, the problem still occurs. This is my first attempt at DXL, so please be gentle with me!

As a quick overview, the script is intended to provide the ability to add cross-references to Object Text. The cross-references can be to Figures, Tables, DOORS Sections or Reference Documents. Hopefully it is commented sufficiently for you to be able to follow what it does, as well as why and how it does it.

Thanks,

Jonathan

Mathias Mamsch - Mon Mar 21 06:21:43 EDT 2011
Hmm... Cannot reproduce the error on my side. When I do as you described the newly created attribute columns vanish from the view and the modules goes to read only without any crashes.

The script is too long for me to spot an error right on the first view. Are you getting a DXL traceback, which tells you where the exception occurs (or just the exception)? This would be extremly helpful in determining the reason for the exception.

So some questions:

• Are there any Triggers on the module which could interfere (e.g. onclose/onopen trigger) and maybe make the module crash? (Try getting the same effect on a module, without any triggers applying)

• Are there DXL layout columns in the view or DXL attributes in the module which could interfere (and crash the module)? (Make sure you try this with a newly created module without any Layouts / DXL Attributes)

llandale - Mon Mar 21 10:23:57 EDT 2011
The diagnostic log itself is not useful, except maybe to 3 people in the world but I'm not one. The DXL errors are more useful, but in this case its in an encrypted file.

-R-E- DXL: <config/menuFns.inc:374> An unexpected error has occurred: doors.exe caused an EXCEPTION_ACCESS_VIOLATION in module doors.exe at 001B:007149EE
Backtrace from <standard/object/properties.dxl:604>

I see the rest of the thread. using v9.2.0.1 I've duplicated your symptoms with your DXL, but more importantly also by manually creating an enumerated attribute type and def. Adding to the view and not saving. So, it does not appear your DXL is at fault (EXCEPT in function updateReferableObjects() you fail to declare variable childObject used at lines 659 and 706; gads that just chaps my hide...).

This is a bug and I really cannot track it down since I lack the un-encrypted version of those include files. Anyway, like the doctor said "Don't do that".

• Louie

llandale - Mon Mar 21 10:23:57 EDT 2011
The diagnostic log itself is not useful, except maybe to 3 people in the world but I'm not one. The DXL errors are more useful, but in this case its in an encrypted file.

-R-E- DXL: <config/menuFns.inc:374> An unexpected error has occurred: doors.exe caused an EXCEPTION_ACCESS_VIOLATION in module doors.exe at 001B:007149EE
Backtrace from <standard/object/properties.dxl:604>

I see the rest of the thread. using v9.2.0.1 I've duplicated your symptoms with your DXL, but more importantly also by manually creating an enumerated attribute type and def. Adding to the view and not saving. So, it does not appear your DXL is at fault (EXCEPT in function updateReferableObjects() you fail to declare variable childObject used at lines 659 and 706; gads that just chaps my hide...).

This is a bug and I really cannot track it down since I lack the un-encrypted version of those include files. Anyway, like the doctor said "Don't do that".

• Louie

Dangthrimble - Mon Mar 21 10:37:28 EDT 2011
I humbly apologise for my heinous crime. To the best of my knowledge I have little (i.e. no) control over my DOORS environment and have no idea how to modify ‘$DOORSHOME/lib/dxl/startup.dxl’ to include ‘XFLAGS_ &=~AutoDeclare_’ (if someone could advise, it would be much appreciated). I presume that would have flagged up my misdemeanour and allowed me to keep it to myself. I will modify the script forthwith, though my crime is now exposed for all to see.

I do, however, feel somewhat vindicated to know that the underlying problem does not lie in my code. For that, I am forever in your debt.

Thanks,

Jonathan